|
|
| Author |
Thread Statistics | Show CCP posts - 15 post(s) |
|
CCP Redundancy
C C P
C C P Alliance
0
   |
Posted - 2011.10.17 14:53:00 -
[1] - Quote
Miraqu wrote:first
So this will be turned on with the next patch?
Or just on SiSi?
Live on TQ clients from tomorrow's patch.
M1AU wrote:
Soooo the only thing that matters for me is: does it use any additional Windows OS components and therefor does it still work on Linux through WINE?
This uses some very standard libraries - I would be surprised if Eve works without this, but doesn't work with it (although that's not a guarantee).
Rees Noturana wrote:
... and Mac?
We tested Macs internally. |
|
|
CCP Redundancy
C C P
C C P Alliance
0
|
Posted - 2011.10.17 15:04:00 -
[2] - Quote
M1AU wrote:Thanks for the reply. Standard libraries sounds good, it's probably just working ootb. Guess we have to wait for tomorrow. (Setting long skill to be trained.)
If you've been on SISI in the last week or so, then you will have been running with this. |
|
|
CCP Redundancy
C C P
C C P Alliance
1
|
Posted - 2011.10.17 15:19:00 -
[3] - Quote
Ronan Teisdari wrote:What is defined as a 'crash' ?
Does that include when clients stop responding, but never close?
Does that include when internet connection drops causing the client to stop receiving packets?
What events will cause the crash report to actually be filed?
(in reverse order)
Technically speaking, unhandled C++ exceptions cause this to trigger. This would probably normally be when the client closes and it asks you if you want to upload the information and check for fixes. I've left the normal windows error reporting in case there is an issue with our stuff.
If the internet drops, no crash information uploads can happen.
When clients stop responding but don't close, that's probably a deadlock or an infinite loop. Neither of these counts as a crash, even if they are sucky.
|
|
|
CCP Redundancy
C C P
C C P Alliance
1
|
Posted - 2011.10.17 15:41:00 -
[4] - Quote
Tippia wrote:I'm a bit curious as to whether this will only catch EVE-specific crashes or whether it will be able to report cider-related ones as well (or, worse, I'd imagine, ones where EVE and cider collude to make my life miserable)?
I haven't been able to test it with a cider crash, but we managed to get a dump from an artificially manufactured crash in our own code. |
|
|
CCP Redundancy
C C P
C C P Alliance
1
|
Posted - 2011.10.17 15:54:00 -
[5] - Quote
Weaselior wrote:That refers to the standard Windows thing, and is unclear on the CCP error reporting.
It's currently mandatory, but we'll patch it asap to make it optional. |
|
|
CCP Redundancy
C C P
C C P Alliance
4
|
Posted - 2011.10.17 16:07:00 -
[6] - Quote
Weaselior wrote:I appreciate that, thanks.
I should probably mention: This doesn't cover the web-browser that we have built in to Eve (it's a different process) - I wouldn't even consider making that mandatory, since you could be interacting with a third party website that we have no business knowing anything about. Most of the rest of the cases of doing stuff in the Eve client already require you to interact with our servers.
This change won't be ready for the patch tomorrow since it will need to be both done and tested. |
|
|
CCP Redundancy
C C P
C C P Alliance
4
|
Posted - 2011.10.17 16:24:00 -
[7] - Quote
Weaselior wrote:Solo Drakban makes a good point - is mandatory reporting being patched out before release, or in winter expansion 1.1
In the short term, if you're worried about this feature then the best workaround would be to block your computer from accessing http://crashes.eveonline.com
This won't cause any issues with Eve, but it will mean that we won't be able to see and fix your crashes. |
|
|
CCP Redundancy
C C P
C C P Alliance
17
|
Posted - 2011.10.18 16:01:00 -
[8] - Quote
Pharuan wrote:I would love to see a graph of the crash data that you have collected thus far.
Imagine a massive red spike on the right hand side that crushes everything else down to insignificance. |
|
|
|
| |
|